Dynamic voip location system

ABSTRACT

A system for determining dynamically any given registered wireless device VoIP location, whereby the dynamic method reports the VoIP address return path as being the VoIP Location into a database. Applications of the system can access the database to contact each individual, specific, fixed or wireless device by VoIP for any data exchange.

BACKGROUND

1. Field of the Invention

The present invention is directed to service providers, telephonycompanies, messaging service companies, notification service companiesor services, database management companies, all for private or publicuse. Specifically, the Dynamic VoIP location system is designed toprovide VoIP location information to a server or multiple servers inorder to enable (a) reliable data exchange from such server or serversto any device connected to the internet and/or (b) communication betweenany different devices connected to the internet to at least one of thesystem servers, provided that any such devices are subscribed to theDynamic VoIP location system server service.

2. Background of the Invention

Current systems and methods for identifying the VoIP location of adevice user (be it a fixed or wireless device) connected to the internetto which to send data to is commonly done by means of the device user,at the time it requires certain data, to then access a so called URI(uniform resource identifier) consisting of a URL (uniform resourcelocator) and a URN (uniform resource name) and receive a reply to its“return path” with the data it required. This ‘return path’ is what werefer to in this invention as the user's device VoIP location.

This commonly used way of receiving data on demand when the userrequires it and extracts it itself through the internet (VoIP) iscumbersome and inflexible as it does not allow receipt of the latest,most up-to-date data or information as and when it becomes available asthe user may simply not know that data he requires is available to him.

More recently systems known as “Push Notification System” have addressedthis as a potential solution, however they do not resolve thereliability aspects in terms of ensuring the return path (i.e. theuser's device VoIP location) is accurate at all times.

In particular when devices connected to the internet, even if subscribedto an existing “Push Notification System”, have the followingproperties:

a.—for example in the case of a fixed device, it may reconnect todifferent VoIP (internet) access points available to it (for example, itmay disconnect from one WiFi router to connect to another different WiFirouter)

b.—for example, in the case of a wireless device such as a mobile phone,it may be on the move and thus change in the mobile network's “LocationArea” (LC). However, even within the same “Location Area” mobilenetworks may have a segmentation of several different cells. Thewireless device VoIP “Routing Area” (RA) may therefore be differentdepending on which cell it's connected to within a certain “LocationArea” (LA). This complexity in mobile networks, where mobile devicesinteract with the mobile network, depending on which state the mobiledevice is in, ensures the mobile network at all times updates the“Routing Area” of each mobile device connected to it. For example whenthe mobile device changes cell, the mobile network updates the mobiledevice “Routing Area”. When it changes “Location Area”, the mobiledevice establishes a new connection and the mobile network records thenew location or “Routing Area” of such a mobile device.

Even the most recent systems, such as those known as “Push Notification”systems, do not have access to mobile operator's mobile devices VoIP“Routing Area”, which would provide the reliable information needed toextract the return path or “VoIP location” described herein. Thisremains a major technical issue still not resolved by the prior artsystems. A key aspect inherent to the complexity of VoIP networks allinterconnected to each other, is that firewalls further complicate andreduce the reliability of most solutions. Another aspect that is notresolved in both fixed and wireless devices, and is most critical inwireless devices, is the power consumption used when having to accessvery often specific URLs to see if any more updated or requiredinformation is available to the fixed or wireless device users, only tofind out (more often than not) that the access, with the correspondingdata use and power consumption, was unnecessary.

Attempts have been made by companies providing automatic PushNotifications to use databases for those devices subscribed to theirsystem. This in itself does not provide a solution to the issuesdescribed before; in particular they do not resolve the near real time“WiFi router” or mobile network “Routing Area” changes (return path—VoIPlocation) nor the minimizing of power consumption.

SUMMARY OF THE INVENTION

The present invention is designed to overcome the shortcomings of theprior art and to provide an automated way of identifying and reportingthose VoIP return paths or “VoIP location” addresses to a database forsubsequent use by all kinds of different applications, with access tosuch database(s) for all those device users connected to the internet(VoIP) and subscribed to the Dynamic VoIP location system describedherein. Moreover the present invention addresses in particular the needfor power consumption reduction, in particular for wireless devicesusing this invention, whilst maintaining the reliability of the nearreal-time updating of the VoIP return paths or “VoIP location” addressesof each mobile device user connected to the internet (VoIP) andsubscribed to this Dynamic VoIP location system described herein.

The present invention is preferably a service offered by VoIP serviceproviders, VoIP telephony companies, VoIP messaging service companies,VoIP notification service companies, VoIP database management companiesor VoIP Data Content Providers.

As a matter of illustration of the present invention, consider the useby a VoIP service provider with registered users using mobile phones,who in the prior art would have an application of a VoIP serviceprovider running permanently on these mobile phones, each connecting toa SIP server at an interval of several seconds. This previous system ormethod, whilst ensuring the return path is known to the SIP server,which can then send incoming calls signalling as and when they happen,becomes unpractical in its daily use at it drains the battery of themobile device.

Other systems known in the prior art make use of so called PushNotification systems, whereby the mobile device application is alsosubscribed to the push notification system of a 3^(rd) party, differentthen the VoIP service provider. In this latter system, the mobile phonehas the VoIP service provider application switched off, waiting for thepush notification system to notify the mobile device with an incomingrequest, be it an incoming message or an incoming call. This previoussystem or method, whilst ensuring the battery use of the mobile deviceis minimal, does not ensure a reliable return path. That is because themobile device may have changed WiFi router or mobile network VoIP“Routing Area”. On many occasions, it would not receive the pushnotification when on the move, and as such this approach becomesimpractical for daily use for mobile devices.

The present invention resolves both key technical aspects of the prior,namely a reliable return path (i.e. VoIP location) whilst ensuringminimal required power consumption. This is achieved by doing thingsdifferently from the prior art. Namely, this invention does not rely onthe mobile network VoIP “Routing Area” as it does not have access to it.Instead however, it relies on the mobile device downloadable softwaremodule, which at any change of VoIP access method or name, authenticatesand connects to the Dynamic VoIP location system to which the mobiledevice is subscribed to and described herein. The combination of thissoftware module (downloadable to each mobile device) together with thedynamic return path (VoIP location) extraction at the server of eachmobile device connected to the server to which it's subscribed to,jointly form the Dynamic VoIP location system. As the mobile softwaremodule additionally checks if any other application is running on themobile device other then itself, including in standby mode, it willclose all other applications (such as for example the application of theprevious mentioned SIP service provider) AND will switch the VoIP accessmethod of the mobile phone to the smallest bandwidth available to suchmobile phone, for example switching from 3G/UMTS?WCDMA to GPRS.

This last action by the software module, reduces the power consumptionof the mobile phone to the lowest possible, whilst still ensuring VoIPconnection by the mobile phone. The mobile network's “Routing Area”still ensures including border areas in coverage, due to the fact thatsmall bandwidth (i.e. GPRS) is more reliable then high bandwidth (i.e.3G). This ensures the highest possible reliability also for the DynamicVoIP location system of this invention.

As stated before, the software module (as a part of the Dynamic VoIPlocation system) is downloadable by a mobile device which will thenconnect and authenticate to the server of the Dynamic VoIP locationsystem at certain time intervals, but in particular at each change ofwireless connection method or name. For example, any time the softwaremodule detects a change from 3G to GPRS or from GPRS to WiFi or fromWiFi router name c to another WiFi router name or from no wireless to awireless connection no GPRS to GPRS or from WiFi loss to GPRS, then thesoftware module will connect at that specific time and authenticate tothe server. When no change is detected for a certain time period then atregular longer time intervals to safe power consumption the softwaremodule will optionally also connect to the server to ensure that when amobile changes cell in a mobile network that this results in aconnection from the software module to the server. In this way theserver will be able to keep the VoIP return path or “VoIP Location” ofeach mobile device registered to the Dynamic VoIP location system up todate.

An object of the present invention is to reduce the time and effort, butmore importantly the probability of error, to synchronize a databasefrom a private individual or business with the database of 3^(rd) party,performed in a fully automated and dynamic manner by the 3^(rd) party,with express consent of such private individual or business.

Another object of the present invention is to provide a system thatmaintains the “VoIP location” or return path of each registered VoIPdevice user updated in a database (for use by applications tocommunicate with each such user at a future time, as described herein)by reducing the power consumption of such registered VoIP user devicesto a minimum.

Re-capping, the invention in a first aspect is a system for detecting ordetermining any given “VoIP location” of any “VoIP enabled deviceregistered to the system” by extracting any such device's “VoIP addressor return path” and storing it and updating it in one or more accessibledatabases, in which: (a) the system is adapted to receive VoIPcommunications from multiple VoIP enabled devices; (b) the systemenables access to information in one or more databases; (c) the systemis capable of extracting and reporting dynamically the “VoIP address orreturn path” and all associated information from each incoming datacommunication from any “VoIP enabled device registered to the system”into a database(s) associated with each corresponding registered VoIPenabled device user account; (d) the system is capable of extracting aspecific “VoIP address or return path” and all associated informationcorresponding to a specific registered VoIP enabled device user accountfrom the system accessible database(s) and communicating with eachspecific VoIP enabled device registered to the system through eachspecific “VoIP address or return path”.

Optional features include the following:

-   -   the “VoIP enabled device registered to the system” incorporates        a “software module”, downloadable to the VoIP enabled device,        which at certain time intervals authenticates and connects to a        server which is part of the system.    -   the server then authenticates if it's a registered VoIP device        user and extracts the “VoIP address or return path” and stores        this data into the registered VoIP enable device user account as        the “VoIP location” and the server can at any time send data to        any specific registered VoIP device user.    -   such time intervals correspond to the times of detection of any        change of VoIP access method or name by the “VoIP enabled device        registered to the system”.    -   the transition from the “VoIP enabled device registered to the        system” changes from not synchronised to synchronised is also        considered a change of VoIP access method or name.    -   the time between each time interval of the registered VoIP        enabled device authenticating and/or connecting with the server        is less than the time allowed by the registered VoIP enabled        device to receive a response from the server.    -   any “VoIP enabled device registered to the system” (VoIP        device 1) can connect to any such other different “VoIP enabled        device registered to the system” (VoIP device 2), the system        comprising: (a) “VoIP device 1” authenticating and connecting to        the system server and providing in its payload data destined for        “VoIP device 2”; (b) the server extracting from the data        communication with “VoIP device 1” the payload data destined for        “VoIP device 2”; (c) the server extracting from its accessible        database the “VoIP location” or “VoIP address or return path” of        “VoIP device 2” and communicating with “VoIP device 2” by        sending it the data and the origin of such data as having been        originated from “VoIP device 1”.    -   any “VoIP enabled device registered to the system” (VoIP        device 3) can send commands to any such other different “VoIP        enabled device registered to the system” (VoIP device 4) the        system comprising: (a) “VoIP device 3” authenticating and        connecting to the system server and providing in its payload a        command known by and destined for “VoIP device 4”; (b) the        server extracting from the data communication with “VoIP device        3” the payload command data destined for “VoIP device 4”; (c)        the server extracting from its accessible database the “VoIP        location” or “VoIP address or return path” of “VoIP device 4”        and communicate with “VoIP device 4” by sending it the command        data; (d) optionally the server sending to its destination “VoIP        device 4” together with the command data also the origin of such        data as having been originated from “VoIP device 3”.    -   the system server can send payload data and/or payload commands        to any individual or such multiple “VoIP enabled device(s)        registered to the system” the system comprising: (a) the system        server extracting from its accessible database(s) the “VoIP        location” or “VoIP address or return path” of any individual or        such multiple “VoIP enabled device(s) registered to the system”        it wishes to communicate with; (b) the server extracting from        its accessible database(s) any such payload data and/or payload        commands; (s) the server send the payload data and/or payload        commands from previous point ‘b’ to all the “VoIP address or        return paths” of previous point ‘a’ corresponding to each unique        “VoIP enabled device(s) registered to the system”.    -   the system server stores the “software module” which can be        downloaded by any “VoIP enabled device”.    -   a “VoIP enabled device” registered to the system is a wireless        enabled VoIP device; for example but not limited to a mobile        phone, mobile smart phone, wireless pc card, wireless module,        wireless tablet, wireless pc.    -   a wireless “VoIP enabled device” can download over the air the        “software module”.    -   the software module is also capable of; (a) detecting if any        other software applications other then this invention's previous        mentioned “software module” is active and (b) if the wireless        “VoIP enabled device” is in the standby mode, then (c) if        previous ‘a’ and ‘b’ are not detected then the “software module”        will disable the highest bandwidth VoIP communication and enable        only the lowest bandwidth VoIP communication method available to        the wireless “VoIP enabled device”, and (d) if the “software        module” detects any of previous ‘a’ or ‘b’ then it will        deactivate previous point ‘c’, meaning it will activate or        enable the highest bandwidth VoIP communication available to the        wireless “VoIP enabled device”.    -   a wireless “VoIP enabled device” registered to the system in        particular includes such “certain time intervals” being        performed at the times of detection of any change of mobile        network cell, wherein the transition from the wireless “VoIP        enabled device registered to the system” changing from not        synchronised to synchronised to a mobile network cell is also        considered a change of VoIP access method or name.    -   a “VoIP enabled device” registered to the system is a wired line        VoIP enabled device; for example but not limited to a tablet,        pc, desktop computer, server.    -   “VoIP” stands for any such data communications protocol; for        example but not limited to: GSM/GPRS, WAP, 3G, UMTS, 4G, WiFi,        Wimax, CDMA, WCDMA, WSCDMA, SCDMA, TDSCDMA, CWTS, CWPAN, PDS,        PHS, Bluetooth, WRP, WNP, WAN, LAN, ATM, ISDN, DSL, ADSL, VDSL,        ISDM, HTML, TCP/IP, HTTP, HTTPS, UDP.

A second aspect is method for detecting or determining any given “VoIPlocation” of any “VoIP enabled device registered to the system” byextracting any such device's “VoIP address or return path” and storingit and updating it in one or more accessible databases, in which themethod is performed by a system as defined above.

Additional features and advantages of the invention will be set forth inthe description which follows, and in part will be apparent from thedescription, or may be learned by practicing the invention. Theobjectives and other advantages of the invention will be realized andattained by the structure particularly pointed out in the writtendescription and claims as well as the drawings hereto.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a schematic diagram of a preferred embodiment of the presentinvention.

FIG. 2 is a flow diagram of a preferred embodiment of the presentinvention.

FIG. 3 is a timing chart of the preferred embodiment of the presentinvention.

FIG. 4 is a timing chart enforcing previous FIG. 3 preferred embodimentof the present invention

DETAILED DESCRIPTION OF THE INVENTION

Referring to FIGS. 1 and 2, a Dynamic VoIP location system which couldbe a private or commercial server 100 (VoIP location server), in anylocation in the world which uses internet services, and which includesone or more databases (VoIP location database) and an external internetaccess c2 to the system 100. Additional external access means to thesystem can also be present. Additional external databases 101 (VoIPlocation database) may be accessible to the system 100. The systemserver 100, could host the ‘software module’ (VoIP location softwaremodule ‘sm’) downloadable into a wireless device; for example the‘software module’ as shown in FIGS. 1 and 2 in each wireless deviceWD_x1 and WD_y1 and WD_wn and WD_zn and so forth in FIG. 1.

To use the “Dynamic VoIP location system” service, the device users mustconnect to the VoIP location server and subscribe to the service. Insome very specific cases, where the information of a specific databaseaccessible to the system consists explicitly and only of publicinformation without any legal restriction on disclosure of any form fromany third party whatsoever, only in this last case potentially nosubscription would be required if so decided by such 3^(rd) party.

The Dynamic VoIP location system consisting of at least one VoIPlocation server ‘100’ and at least two or more devices that incorporatea ‘sm’(VoIP location software module). The VoIP location serverpreferably keeps a record of the subscribers (with their expressconsent) in a database 101, preferably resident within the same server100 and stores their user identification and originating VoIP address orVoIP return path (referred to herein as the user's “VoIP location”) toreply to.

In the example shown in FIG. 1, it is assumed that wireless devices aresubscribed the Dynamic VoIP location system (100) and have a VoIPlocation software module (sm) embedded in each user's wireless device.All wireless devices with a built in ‘sm’ authenticate and communicatewith server 100 even when the wireless device is in standby mode. The‘sm’ communicates with server 100 after wireless device power-up andeach time the wireless device changes VoIP access name (for example whenchanging between any of the following 3G, GPRS, WiFi or between any ofthe previous and a new different to the previous WiFi router name andwhen changing between mobile cells. The ‘sm’ will force the wirelessdevice to close any such other applications different from the ‘sm’itself that requires VoIP connection and additionally will force thewireless device to switch to the lowest available bandwidth VoIP accessmeans, for example switch from 3G/WCDMA to GPRS, as shown in FIG. 2.

The VoIP location server 100 will, each time a wireless device (WD_X1,WD_zn, etc.) with a built in VoIP location software module ‘sm’subscribed to the Dynamic VoIP location system connects with the server,store the return response path referred to in this invention as eachwireless device user's VoIP Location and which for example willcorrespond in the event of a wireless device connect through GPRS withits unique PSPDN (packet switched public data network) address at suchtime.

As a matter of illustration of the workings of the Dynamic VoIP locationsystem, wherein 3G enabled wireless device WD_y1 wishes to call 3Genabled wireless device WD_x1, where both devices incorporate a SIPsoftware application that enables VoIP conversations and incorporatealso this invention's VoIP location software module ‘sm’. Both WD_x1 andWD_y1 latest VoIP location (VoIP return path or also known in theindustry as PSPDN (packet switched public data network) address isstored in VoIP Location server 100 or in external database 101accessible to the server 100 and updated by the wireless devices asdescribed herein before. The ‘sm’ in both wireless devices have switchedthe wireless devices to the least power consuming GPRS instead of thehigher power consuming 3G.

As illustrated in FIG. 2 Wireless device user WD_y1 starts opening itsSIP application (wireless device exits standby state), whereby ‘sm’switches WD_y1 from GPRS to 3G (highest available VoIP bandwidth) andthe user initiates a SIP to WD_x1 who is in standby mode through VoIPconnections c3-c6 and c14. The VoIP SIP server informs VoIP locationserver 100 through connection c15 of a call request originated by WD_y1and destined for WD_x1. The VoIP location server 100 will reply with thelatest VoIP location address available in its database of WD_x1 throughconnections c2 and c1-c5 and send data with instructions for WD_x1 VoIPlocation software module ‘sm’ to switch from GPRS to 3G (highestavailable VoIP bandwidth) and activate the corresponding SIP applicationto allow it to receive the incoming call ringing signalling, oralternatively to notify the user of WD_x1 with a notification of anincoming call such that the user can accept or reject it. In the eventof acceptance of the incoming notification the corresponding action willbe automatically performed by the ‘sm’, for example activate thecorresponding SIP application as to accept the incoming call requestoriginated by WD_y1.

Referring to FIGS. 3 and 4, these show the timing of communicationsbetween the two main parts of the Dynamic VoIP location system, namelybetween VoIP location software module ‘sm’, referred to in FIGS. 3 and 4as “Client Ping” and VoIP Location server ‘100’ , referred to in FIGS. 3and 4 as “Server Reply”. It illustrates the same previous example of aSIP call originated by WD_y1, referred to in FIGS. 3 and 4 as ‘Call 1’and a subsequent later call also originated by WD_y1 referred to as‘Call 2’. Both ‘Call 1’ and ‘Call 2’ are destined for WD_x1, asexplained herein. The time ‘Pt’ refers to the time between twoconsecutive communications (VoIP location updates) between WD_x1 andserver 100 and the corresponding VoIP location update in the database100 or 101 corresponding to WD_x1. The timing ‘Re is the time thesoftware module ms’ allows the server 100 to send a reply that WD_x1would deem acceptable as valid. This time ‘Rt’ is defined by thewireless device's ‘sm’ as ‘Rt’ being bigger then ‘Pt’ when communicatingwith server 100. It is important to note, that the time ‘Pt’ may varybetween consecutive ‘Pt's’ and the ‘sm’ also dynamically adapts theallowed ‘Rt’ by server 100 in compliance with previous condition of‘Rt’>‘Pt’. It is also important to note that the server 100 does notnecessarily reply to ‘sm’ communications for VoIP Location updates, butsimply extracts and stores the VoIP Location address in thecorresponding database user data and only replies to the correspondingwireless device's ‘sm’ exactly at the time when the server 100 has datafor a specific subscribed user's ‘sm’ (be it a notification of some sortor a message or an incoming call and so forth). This last is in factpossible to be instant—i.e. at the time the server 100 has data to besent to a specific device's ‘sm’ because of the condition of ‘Rt’(allowed response time of server 100) >‘Pt’ (time between twoconsecutive VoIP location updates by a device's software module ‘sm’).

This automated dynamic way of obtaining the “VoIP Location” between anincoming VoIP location update request and any available VoIP locationaddress available in the database 100 or 101 is generally very fastbecause VoIP (voice over internet protocol) access and database accessis generally fast. Furthermore, as reducing power consumption to aminimum whilst maintaining high reliability of updating the VoIPlocation corresponding to each user subscribed to the

Dynamic VoIP Location system, it is crucial that it is understood thatthe software modules ‘sm’ together with the VoIP Location server “100′which includes a VoIP Location database inside ‘100’ or separate as‘101’ together form the Dynamic VoIP Location system.

Any of the various components or sub-steps disclosed above can be usedeither alone, or in multiple parallel set-ups, or with other components,or with components or features of the present invention.

It will be apparent to those skilled in the art that variousmodifications and variations can be made to the “Dynamic VoIP Locationsystem”, “VoIP Location server” or “VoIP Location software module” ofthe present invention without departing from the spirit or scope of theinvention.

The foregoing disclosure of embodiments of the present invention hasbeen presented for purposes of illustration and description. It is notexhaustive or intended to limit the invention to the precise formsdisclosed herein. Many variations and modifications of the embodimentsdescribed herein will be obvious to one of ordinary skill in the art inlight of the above disclosure. The scope of the invention is to bedefined only by the claims appended hereto, and by their equivalents.

1. A system for detecting or determining any given “VoIP location” ofany “VoIP enabled device registered to the system” by extracting anysuch device's “VoIP address or return path” and storing it and updatingit in one or more accessible databases, in which: (a) the system isadapted to receive VoIP communications from multiple VoIP enableddevices; (b) the system enables access to information in one or moredatabases; (c) the system is capable of extracting and reportingdynamically the “VoIP address or return path” and all associatedinformation from each incoming data communication from any “VoIP enableddevice registered to the system” into a database(s) associated with eachcorresponding registered VoIP enabled device user account; (d) thesystem is capable of extracting a specific “VoIP address or return path”and all associated information corresponding to a specific registeredVoIP enabled device user account from the system accessible database(s)and communicating with each specific VoIP enabled device registered tothe system through each specific “VoIP address or return path”.
 2. Thesystem of claim 1 where the “VoIP enabled device registered to thesystem” incorporates a “software module”, downloadable to the VoIPenabled device, which at certain time intervals authenticates andconnects to a server which is part of the system.
 3. The system of claim2 where the server then authenticates if it's a registered VoIP deviceuser and extracts the “VoIP address or return path” and stores this datainto the registered VoIP enable device user account as the “VoIPlocation” and the server can at any time send data to any specificregistered VoIP device user.
 4. The system of claim 2 where such timeintervals correspond to the times of detection of any change of VoIPaccess -method or -name by the “VoIP enabled device registered to thesystem”.
 5. The system of claim 4 where the transition from the “VoIPenabled device registered to the system” changes from not synchronisedto synchronised is also considered a change of VoIP access method orname.
 6. The system according to claim 2 to claim 5, wherein the timebetween each time interval of the registered VoIP enabled deviceauthenticating and/or connecting with the server is less than the timeallowed by the registered VoIP enabled device to receive a response fromthe server.
 7. The system of claim 1, wherein any “VoIP enabled deviceregistered to the system” (VoIP device 1) can connect to any such otherdifferent “VoIP enabled device registered to the system” (VoIP device2), the system comprising: (a) “VoIP device 1” authenticating andconnecting to the system server and providing in its payload datadestined for “VoIP device 2”; (b) the server extracting from the datacommunication with “VoIP device 1” the payload data destined for “VoIPdevice 2”; (c) the server extracting from its accessible database the“VoIP location” or “VoIP address or return path” of “VoIP device 2” andcommunicating with “VoIP device 2” by sending it the data and the originof such data as having been originated from “VoIP device 1”.
 8. Thesystem of claim 1, wherein any “VoIP enabled device registered to thesystem” (VoIP device 3) can send commands to any such other different“VoIP enabled device registered to the system” (VoIP device 4) thesystem comprising: (a) “VoIP device 3” authenticating and connecting tothe system server and providing in its payload a command known by anddestined for “VoIP device 4”; (b) the server extracting from the datacommunication with “VoIP device 3” the payload command data destined for“VoIP device 4”; (c) the server extracting from its accessible databasethe “VoIP location” or “VoIP address or return path” of “VoIP device 4”and communicate with “VoIP device 4” by sending it the command data; (d)optionally the server sending to its destination “VoIP device 4”together with the command data also the origin of such data as havingbeen originated from “VoIP device 3”.
 9. The system of claim 1, whereinthe system server can send payload data and/or payload commands to anyindividual or such multiple “VoIP enabled device(s) registered to thesystem” the system comprising: (a) the system server extracting from itsaccessible database(s) the “VoIP location” or “VoIP address or returnpath” of any individual or such multiple “VoIP enabled device(s)registered to the system” it wishes to communicate with; (b) the serverextracting from its accessible database(s) any such payload data and/orpayload commands; (s) the server send the payload data and/or payloadcommands from previous point ‘b’ to all the “VoIP address or returnpaths” of previous point ‘a’ corresponding to each unique “VoIP enableddevice(s) registered to the system”.
 10. The system according to claim2, wherein the system server stores the “software module” which can bedownloaded by any “VoIP enabled device”.
 11. The system according toclaim 1, wherein “VoIP enabled device” registered to the system is awireless enabled VoIP device; for example but not limited to a mobilephone, mobile smart phone, wireless pc card, wireless module, wirelesstablet, wireless pc.
 12. The system according to claim 2, wherein awireless “VoIP enabled device” can download over the air the “softwaremodule”.
 13. The system of claim 12 wherein such software module is alsocapable of (a) detecting if any other software applications other thenthis invention's previous mentioned “software module” is active and (b)if the wireless “VoIP enabled device” is in the standby mode, then (c)if previous ‘a’ and ‘b’ are not detected then the “software module” willdisable the highest bandwidth VoIP communication and enable only thelowest bandwidth VoIP communication method available to the wireless“VoIP enabled device”, and (d) if the “software module” detects any ofprevious ‘a’ or ‘b’ then it will deactivate previous point ‘c’, meaningit will activate or enable the highest bandwidth VoIP communicationavailable to the wireless “VoIP enabled device”.
 14. The systemaccording to claim 1, wherein a wireless “VoIP enabled device”registered to the system in particular includes such “certain timeintervals” being performed at the times of detection of any change ofmobile network cell, wherein the transition from the wireless “VoIPenabled device registered to the system” changing from not synchronisedto synchronised to a mobile network cell is also considered a change ofVoIP access method or name.
 15. The system according to claim 1, whereina “VoIP enabled device” registered to the system is a wired line VoIPenabled device; for example but not limited to a tablet, pc, desktopcomputer, server.
 16. The system according to claim 1, wherein “VoIP”stands for any such data communications protocol; for example but notlimited to: GSM/GPRS, WAP, 3G, UMTS, 4G, WiFi, Wimax, CDMA, WCDMA,WSCDMA, SCDMA, TDSCDMA, CWTS, CWPAN, PDS, PHS, Bluetooth, WRP, WNP, WAN,LAN, ATM, ISDN, DSL, ADSL, VDSL, ISDM, HTML, TCP/IP, HTTP, HTTPS, UDP.17. A method for detecting or determining any given “VoIP location” ofany “VoIP enabled device registered to the system” by extracting anysuch device's “VoIP address or return path” and storing it and updatingit in one or more accessible databases, in which the method is performedby a system as defined in claim 1.